File naming for Phoenix data products

Starting Spacecraft Clock time.

Special processing designator to be defined later. This character is used to indicate off-nominal or special processing of the image. Examples might be use of different correlation parameters, special stretches to eliminate shadows, reprocessing with different camera pointing, etc.

The meaning of any individual character in this field will be defined on an ad-hoc basis as needed during the mission. Within one Activity ID, the character will be used consistently, so this field can be used to group together all derived products resulting in one kind of special processing. An attempt will be made to maintain consistency across different Activity ID's as well, but this may not always be possible; thus the meaning of characters may change across different Activity ID's.

A text file will be maintained containing all special processing designators that are used, the Activity ID's they relate to, and a description of the special processing that was done. This file will be included in the PDS archive.

Activity ID as extracted from round-trip accountability Token. Valid values are assigned at planning time by PSI tool.

Identifier of Payload type as extracted from round-trip accountability Token. 1 Hex character representing 4 bits of the 32-bit Token based on a bit lookup, which follows:

Camera eye

Spectral filter position or LED status

Separator, always an underscore.

EDR revision number, 0-255, represented at a 2-digit Hex value.

Separator, always an underscore.

Length of records represented as a 5-digit Hex value.

Ops Token Token value represented as an 8-digit Hex value.

Separator, always an underscore.

Separator, always an underscore.

Last 4 digits of PSI Token (Instrument + Command IDs = MET ID).

Engineering parameter abbreviation.

Separator, always an underscore.

Product identifier. Refer to Phoenix data product types for a list of possible values.

Separator, always an underscore.

Identifier of "primary" instrument.

Identifier of "secondary" instrument.

Specifies number of Solar days since first full day on Mars. Landing day is Sol one ("001"). This field is defined as the primary Sol for this mosaic. For most (and all automatically-produced) products, this is extracted from the input image with the earliest (i.e. lowest) SCLK.

Product identifier. Refer to Phoenix data product types for a list of possible values.

Separator, always an underscore.

Projection type. Indicates the projection or perspective of the product.

Specifies Geometry Correction flag. Indicates what kind of geometric correction has been applied to data. If multiple types of corrections were applied, then the highest-level (in the table below) value is used.

Specifies coordinate frame in which the mosaic is generated. Note that the instance of frames (e.g. Payload) is not specified and must be obtained from label.

Specifies Brightness Correction flag indicating what kind of brightness (radiometric) seam-matching process has been applied to the mosaic. Brightness correction is a seam-matching process done on top of radiometric correction in order to make the mosaic look better; some radiometric accuracy is lost in the process. If multiple types of correction are done, the highest-level (last in the table) value is used.

NOTE: If any kind of brightness matching is applied, the inputs must first be radiometrically corrected. This is stated explicitly in the filename by <prod>, or implicitly if <prod> is not a radiometrically-corrected type, meaning that MIPLRAD has been used.

Activity ID as extracted from round-trip accountability Token. Valid values are assigned at planning time by PSI tool.

Identifier of Payload type as extracted from round-trip accountability Token. 1 Hex character representing 4 bits of the 32-bit Token based on a bit lookup, which follows:

Special processing designator to be defined later. This character is used to indicate off-nominal or special processing of the image. Examples might be use of different correlation parameters, special stretches to eliminate shadows, reprocessing with different camera pointing, etc.

The meaning of any individual character in this field will be defined on an ad-hoc basis as needed during the mission. Within one Activity ID, the character will be used consistently, so this field can be used to group together all derived products resulting in one kind of special processing. An attempt will be made to maintain consistency across different Activity ID's as well, but this may not always be possible; thus the meaning of characters may change across different Activity ID's.

A text file will be maintained containing all special processing designators that are used, the Activity ID's they relate to, and a description of the special processing that was done. This file will be included in the PDS archive.

Valid values are:

Camera eye

Specifies 3 spectral filter positions, LED settings, or color space components. Additional values were planned in the case of color mosaics and mosaics with more than three bands. However, such mosaics were never archived. Refer to the camera EDR and RDR Software Interface Specification (SIS) document for the full description.

Identifier for the institution/team that created the product.

Version identifier providing uniqueness for book keeping. The valid values, in their progression, are as follows:

Range 1 thru 9 - “1”, “2”… “9”

Range 10 thru 35 - “A”, “B” …“Z”

For images, the Version number increments by one whenever an otherwise-identical filename would be produced, independent of the Special field. Thus, even though the Special field may change, the Version number continues to increment by one over the previous Version. This allows the "best" Version of a product to be determined - irrespective of what special processing was done to achieve it - by simply looking for the highest Version number.

The following examples show how the Version field increments independently of the Special field thru a progression of RDR processing for the same SCLK product:

Product type extension.